From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#49504: Server support for Freedesktop.org startup notification Date: Sat, 10 Jul 2021 17:30:21 +0300 Message-ID: <83y2aeb5s2.fsf@gnu.org> References: <83zguubazg.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27691"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 49504@debbugs.gnu.org To: Peter Oliver Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jul 10 16:31:11 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m2E0b-00073S-CZ for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 10 Jul 2021 16:31:09 +0200 Original-Received: from localhost ([::1]:60924 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m2E0a-000360-BU for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 10 Jul 2021 10:31:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50948) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m2E0T-00035o-SR for bug-gnu-emacs@gnu.org; Sat, 10 Jul 2021 10:31:01 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49902) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1m2E0T-0005Io-KJ for bug-gnu-emacs@gnu.org; Sat, 10 Jul 2021 10:31:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1m2E0T-0004sD-I8 for bug-gnu-emacs@gnu.org; Sat, 10 Jul 2021 10:31:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 10 Jul 2021 14:31:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 49504 X-GNU-PR-Package: emacs Original-Received: via spool by 49504-submit@debbugs.gnu.org id=B49504.162592744618710 (code B ref 49504); Sat, 10 Jul 2021 14:31:01 +0000 Original-Received: (at 49504) by debbugs.gnu.org; 10 Jul 2021 14:30:46 +0000 Original-Received: from localhost ([127.0.0.1]:33215 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1m2E0E-0004ri-7x for submit@debbugs.gnu.org; Sat, 10 Jul 2021 10:30:46 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:53142) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1m2E0C-0004r4-JS for 49504@debbugs.gnu.org; Sat, 10 Jul 2021 10:30:45 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34308) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m2E07-00055C-42; Sat, 10 Jul 2021 10:30:39 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4534 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m2E02-0006G8-34; Sat, 10 Jul 2021 10:30:38 -0400 In-Reply-To: (message from Peter Oliver on Sat, 10 Jul 2021 13:56:11 +0100 (BST)) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:209745 Archived-At: > Date: Sat, 10 Jul 2021 13:56:11 +0100 (BST) > From: Peter Oliver > cc: 49504@debbugs.gnu.org > > > 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.