Subject: Re: bug#49504: Server support for Freedesktop.org startup notification

From: Eli Zaretskii <[email-masked]>
Date: Sat, 10 Jul 2021 17:30:21 +0300

> Date: Sat, 10 Jul 2021 13:56:11 +0100 (BST)
> From: Peter Oliver <[email-masked]>
> cc: [email-masked]
> 
> > You want to make the Emacs frame displayed due to an emacsclient
> > request show emacsclient as its "exec"?  But then what happens if the
> > user uses that frame for displaying other windows and buffers, which
> > have nothing to do with the original emacsclient request?
> 
> Here’s an example of a feature enabled by the startup notification protocol.
> 
> When a user clicks on an icon for an application in a desktop’s launcher, the launcher will provide feedback to the user that something is happening, perhaps by changing the pointer to the “busy” indicator.  That feedback will be cleared once the application displays a window.  For the launcher to know when to clear the feedback, it needs to know that a particular window is associated with a particular application launch.
> 
> So, in the case you describe, where the user goes on to display other buffers, nothing happens, and that’s fine.

But that was only an example, right?  I asked a more general question.

Emacs is different from many, if not most, applications in this
regard.  For example, it can start any number of windows from the same
"launch".  I'm asking whether we are going to use desktop features
that don't really fit Emacs.