RE: Dialog from emacsclientw.exe must be dismissed (was RE: Best practices for launching Emacs on Windows 7/8)

["Ludwig, Mark" <ludwig.mark@siemens.com>]

> From: Juanma Barranquero, Thursday, June 27, 2013 3:50 PM
> 
> User expectatives for a console program and a GUI one are quite different.

Sure.

There is no "GUI" version on Unix.

I actually don't agree that emacsclientw is a proper "GUI program."  I
suppose you'll take the technical view that it is because it's a
"Windows-mode" not a "console-mode" program, but for a user, it
certainly isn't interactive in any /meaningful/ way.  Popping up
output-only dialogs and making a user click OK does not a GUI program
make.

This emacsclientw variant exists solely on Windows.  Why?  I assume
because the alternative is worse!  The console-mode version
(emacsclient) is even more annoying because Windows pops up a console
to invoke emacsclient every time.  In that configuration, the same
error message goes to the console and then the console window
disappears.  It all happens as a flash.

So, what about emacsclient Unix?  What happens in X in this scenario?
I stopped using Unix as my desktop so long ago that I have no idea
what "launching from a GUI" looks like any more.  Where does the error
message from emacsclient go?  Does the user normally get a chance to
even see it?  What I recall was that launching was in the background
so that stdout/stderr usually went to /dev/null (effectively) ... but
perhaps things have changed.

Cheers,
Mark