Re: w32 does not have emacsclient/server

[Jason Rumney]

Juanma Barranquero <address@hidden> writes:

>   - It's an incompatible change, if small: --socket-name does not
> exist, and you *must* use either the EMACS_SERVER_FILE environment
> variable or the --server-file argument to emacsclient; otherwise
> emacsclient will refuse to work.

That is bad. The original suggestion was to have a standard file
name for the server file.