> Date: Tue, 08 May 2012 14:34:22 -0400 (EDT) > From: Gary Oberbrunner <ga...@genarts.com> > Cc: drew adams <drew.ad...@oracle.com>, help-emacs-windows@gnu.org, lennart > borgman <lennart.borg...@gmail.com>, matthew fidler > <matthew.fid...@gmail.com>, adamdold...@adamgolding.com > > > The latter, of course. The rule is, when you don't have a program to > > wait for Emacs to finish editing, use emacsclientw, otherwise use > > emacsclient. > > You know more than I about these things, I'm sure, but this doesn't seem > accurate to me. > > As far as I can tell, emacsclientw is a GUI program and emacsclient is a CLI > program. Both wait for the server to finish before they return, unless you > use -n, in which case both of them return right away. > > Perhaps a better rule is, when the invoking program is a GUI program (e.g. > you're in a shell within emacs), use emacsclientw (emacsclient pops up an > annoying console window in this case); when the invoking program is a CLI > program where you want messages to come out on stdout, use emacsclient. > > Does that work?
That's another way of putting the same condition, yes.
