On 7/15/05, Stefan Monnier <[EMAIL PROTECTED]> wrote: > Actually, I don't think so. IIRC What we need for emacsclient/server to > work on Windows is to make it work over TCP sockets rather than only over > Unix sockets (because Windows supports TCL sockets but not Unix sockets).
I'm taking a stab at this. Modifying server.el to use TCP sockets is trivial, and modifying emacsclient.c should not be hard *if* the Unix socket support is to be scrapped. > in server.el, use a TCP server socket (on a non-specified port). > Once opened, check to see which port was used. Write the port > and hostname together with a secret random string into > ~/.emacs_server. When a connection comes in, check that the > first bytes sent are exactly the same as the random string I suppose this is to avoid choosing a port number as the standard "Emacs server port"? I'd rather choose a number, and let the user set it up on server.el and pass it to emacsclient.c in case there's a conflict on her system... Another parameter to pass would be the ip address, wouldn't? I'm assuming it's frequent on non-Windows environments to emacsclient against an Emacs server at another machine... -- /L/e/k/t/u _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel