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

[Juanma Barranquero]

On Thu, Jun 27, 2013 at 11:35 PM, Ludwig, Mark <ludwig.mark@siemens.com> wrote:

> 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.

Programs come in all sizes and functionalities.

> 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.

Yes, emacsclientw exists to avoid creating an annoying console in uses
such as yours, i.e., when used as file associations.

> 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.

I do not use Unix-like systems either, at least not frequently. And
I've never run emacsclient from GNU/Linux.

    Juanma