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. For a file association they work the
same as far as I can tell. I.e., after a double-click to open,
Windows Explorer was not going to wait anyway - so it does not
make any difference. (I certainly do not see any command window
popping up with emacsclient. I think there may have been such an
issue with gnuclient.) The waiting capability is useful when you
want to specify a text editor to be invoked by some program that
will subsequently treat the edited file. You can observe the
difference in behaviour by running it from the command line. In
Emacs, I get the "When done with a buffer, type C-x #" prompt
either way; and I ignore it with no apparent harmful effect,
since I have no programs that invoke emacsclient and do wait for
it.
Regards,
David V.
----- Original Message -----
From: "Francis Wright" <f.j.wri...@qmul.ac.uk>
To: "'David Vanderschel'" <d...@austin.rr.com>;
<help-emacs-windows@gnu.org>
Sent: Wednesday, January 05, 2011 6:48 AM
Subject: RE: [h-e-w] Multiple versions of Emacs under Windows;How
to specify which Emacs should run when file is double-clicked?
You probably want to set the file association to emacsclientw.exe
(note the w)
to avoid a command window popping up. And if you want
emacsclient(w).exe to fire
up emacs if it is not already running then you need to specify
runemacs as the
alternate editor, via either a command option or an environment
variable. I
don't think it matters much which version of emacsclient(w).exe
you run, or
where it is. It invokes the version of runemacs as alternate
editor specified
explicitly (if you give it a full path name) or implicitly (if
you don't give it
a full path name) as the first version found via your path
environment variable.
Francis
