unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Ruffing <public@timruffing.de>
To: Po Lu <luangruo@yahoo.com>
Cc: 49505@debbugs.gnu.org,
	Manuel Uberti <manuel.uberti@inventati.org>,
	Peter Oliver <p.d.oliver@mavit.org.uk>,
	Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#49505: 28.0.50; Multiple launchers in GNOME
Date: Tue, 24 May 2022 16:10:38 +0200	[thread overview]
Message-ID: <22c25a5ab2fde02ff8068e65805c74f88a7a0b60.camel@timruffing.de> (raw)
In-Reply-To: <87leurkq2j.fsf@yahoo.com>

Thanks for the comments.

On Tue, 2022-05-24 at 21:39 +0800, Po Lu wrote:
> We can have fine-grained control over WM_CLASS (despite whatever the
> toolkit does), since Emacs can use X Windows requests to directly set
> the WM_CLASS property, but changing that for individual frames based
> on
> how they were created sounds excessive to me.

Note that we wouldn't need to do it for individual frames. If emacs was
started in non-daemon mode, we would use some string X for all its
frames, and if emacs was started in daemon mode, we would use some
string Y for all its frames. 

But as I said, I also prefer the approach that has only a single
.desktop file, so we wouldn't need to bother with this at all.

Best,
Tim
  





  reply	other threads:[~2022-05-24 14:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-10 13:38 bug#49505: 28.0.50; Multiple launchers in GNOME Manuel Uberti
2021-07-10 14:48 ` Manuel Uberti
2021-07-10 16:31 ` Lars Ingebrigtsen
2021-08-10 21:22   ` Peter Oliver
2021-08-11  5:00     ` Manuel Uberti
2021-08-11 17:34       ` Peter Oliver
2021-08-11 17:52         ` Manuel Uberti
2021-10-09 11:19           ` Peter Oliver
2021-10-09 11:29             ` Lars Ingebrigtsen
2021-10-09 15:08               ` Manuel Uberti
2022-05-24 12:33                 ` Tim Ruffing
2022-05-24 13:39                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-24 14:10                     ` Tim Ruffing [this message]
2022-05-25  0:16                   ` Lars Ingebrigtsen
2022-06-20 19:13                   ` Peter Oliver
2022-09-20 12:19                     ` bug#49505: bug#51749: 29.0.50; Emacs 29 Creates Only Emacsclient Icon in Ubuntu Dock Lars Ingebrigtsen
2023-09-03  8:50                       ` Stefan Kangas
2021-08-11 11:10     ` bug#49505: 28.0.50; Multiple launchers in GNOME Lars Ingebrigtsen
2021-07-11 17:06 ` Manuel Uberti
2021-07-25  6:38 ` Manuel Uberti
2021-08-11 10:19   ` Utkarsh Singh
2021-10-04  5:38 ` Manuel Uberti
2021-10-04  9:34   ` Lars Ingebrigtsen
2021-10-07 11:21   ` Simen Heggestøyl
2021-10-07 18:10     ` Lars Ingebrigtsen
2021-10-08 13:02       ` Simen Heggestøyl
2021-10-09 11:18         ` Lars Ingebrigtsen

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=22c25a5ab2fde02ff8068e65805c74f88a7a0b60.camel@timruffing.de \
    --to=public@timruffing.de \
    --cc=49505@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    --cc=manuel.uberti@inventati.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).