From: Eli Zaretskii <eliz@gnu.org>
To: Peter Oliver <p.d.oliver@mavit.org.uk>
Cc: 49504@debbugs.gnu.org
Subject: bug#49504: Server support for Freedesktop.org startup notification
Date: Sat, 10 Jul 2021 15:37:55 +0300 [thread overview]
Message-ID: <83zguubazg.fsf@gnu.org> (raw)
In-Reply-To: <d4262993-ce9e-a956-e4ee-e4421ca74f73@froglet.home.mavit.org.uk> (message from Peter Oliver on Sat, 10 Jul 2021 12:43:39 +0100 (BST))
> Date: Sat, 10 Jul 2021 12:43:39 +0100 (BST)
> From: Peter Oliver <p.d.oliver@mavit.org.uk>
>
> For a desktop environment, it’s helpful to know which execs caused which windows to be opened. One way of doing this is with the Freedesktop.org startup notification protocol, https://specifications.freedesktop.org/startup-notification-spec/startup-notification-latest.txt.
>
> We currently partially support this protocol in GTK builds, because GTK handles it for us automatically. However, GTK can only automatically handle the simple case where emacs is launched and displays a window itself.
>
> To support emacsclient, where the execed process is not necessarily an ancestor of the process displaying the window, as I understand it we’d need to do the following:
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?
next prev parent reply other threads:[~2021-07-10 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 11:43 bug#49504: Server support for Freedesktop.org startup notification Peter Oliver
2021-07-10 12:37 ` Eli Zaretskii [this message]
2021-07-10 12:56 ` Peter Oliver
2021-07-10 14:30 ` Eli Zaretskii
[not found] ` <handler.49504.B.16259174312311.ack@debbugs.gnu.org>
2021-07-10 12:41 ` bug#49504: Acknowledgement (Server support for Freedesktop.org startup notification) Peter Oliver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zguubazg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49504@debbugs.gnu.org \
--cc=p.d.oliver@mavit.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).