I am trying to set up the emacs server daemon and use emacsclientw on MS Windows so that files can be opened into the existing emacs instance without the delay and overhead associated with starting additional instances of emacs for each file opened. An example describing steps to configure the emacs daemon and client on Windows is provided in the emacswiki for MS Windows:
https://www.emacswiki.org/emacs/EmacsMsWindowsIntegration#toc7 But like an earlier poster I had no success. http://lists.gnu.org/archive/html/help-emacs-windows/2017-04/msg00022.html Can anyone provide an example for MS Windows showing how to run the daemon on startup and have all files open into a single emacs instance? Here are my results using the steps described in the wiki which involves: Running emacs as a daemon, runemacs.exe --daemon Followed by invoking emacsclientw.exe with the appropriate options. Starting the daemon succeeds (I see emacs.exe in the process list), but invoking emacsclient produces errors. The wiki says to create a shortcut to emacsclientw.exe and change the target to X:\path\to\emacs\bin\emacsclientw.exe -na "X:\path\to\emacs\bin\emacsclientw.exe" -c -n Is this correct? It looks like the client is invoked twice. Using the target as shown does not run the program and produces the error "file name or argument required". Using only the first part of the target shown above X:\path\to\emacs\bin\emacsclientw.exe -na produces a generic error. Using only the second part X:\path\to\emacs\bin\emacsclientw.exe -c -n produces the error "No socket or alternate editor." (The official emacsclient options are described here.) Any suggestions? Emacs runs fine in standard mode, that is, not in daemon mode. Version 25.1. I would prefer to run the daemon rather than starting the server in my initialization file. -- km
