One clearly visible difference between emacsclient and emacsclientw is that emacsclient sends error messages to the console whereas emacsclientw pops up a dialogue box. You can see this easily by running both with no arguments at a command prompt.
Francis > -----Original Message----- > From: Jason Rumney [mailto:jasonrum...@gmail.com] On Behalf Of Jason > Rumney > Sent: 05 January 2011 10:59 pm > To: David Vanderschel > Cc: Francis Wright; help-emacs-windows@gnu.org > Subject: Re: [h-e-w] Multiple versions of Emacs under Windows; How to specify > which Emacs should run when file is double-clicked? > > "David Vanderschel" <d...@austin.rr.com> writes: > > > I believe that the difference between emacsclient and emacsclientw is > > that, with the "w", it is equivalent to emacsclient with the --no-wait > > option and not whether or not a command window appears. > > No, both versions wait. The difference is that emacsclientw.exe is compiled as a > Windows program, and emacsclient.exe is compiled as a console program. At > least on older versions of Windows a console program always resulted in a > command window opening when lauched outside of a command window. And > being a Windows program, the console window does not wait for > emacsclientw.exe to terminate before returning you to the prompt, so in that > context it does appear not to wait (but for text editors that wait for the > subprocess to terminate, it should still work the same as emacsclient.exe).
