[Please keep the list address on the CC.] > From: Kerry Maize <kerryma...@gmail.com> > Date: Mon, 18 Sep 2017 17:31:49 -0400 > > Starting the server daemon appears to succeed. From the command prompt > in the emacs bin directory > > X:\path_to\emacs\bin>runemacs.exe --daemon > > starts the daemon. That is, the emacs.exe process starts and is > visible in the process list of Windows Task Manager. No gui frame is > invoked. > > Now for the client: > > X:\path_to\emacs\bin>emacsclientw.exe > > with no arguments pops a dialog error: > > "emacsclientw.exe: file name or argument required"
This is expected: it really does need a file name. > If I invoke the client with a filename: > > X:\path_to\emacs\bin>emacsclientw.exe "X:\Text.txt" > > pops the dialog error: > > "emacsclientw.exe: No socket or alternate editor. Please use: > --server-file (or environment variable EMACS_SERVER_FILE) > --alternate-editor (or environment variable ALTERNATE_EDITOR)" This I cannot reproduce: it works for me. After you start the daemon, do you see a file ~/.emacs.d/server/server under your home directory? Also, are you sure emacsclientw.exe you are invoking is from the same Emacs version as the Emacs itself? And finally, does the shell window from which you invoke emacsclientw.exe have the HOME directory set to the same place as the shell where you invoked Emacs? Do you have the HOME environment variable set, or do you rely on the default location?