From: "Simen Heggestøyl" <simenheg@runbox.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 49505@debbugs.gnu.org,
Manuel Uberti <manuel.uberti@inventati.org>,
Peter Oliver <p.d.oliver@mavit.org.uk>
Subject: bug#49505: 28.0.50; Multiple launchers in GNOME
Date: Fri, 08 Oct 2021 15:02:20 +0200 [thread overview]
Message-ID: <87r1cvwtyb.fsf@runbox.com> (raw)
In-Reply-To: <87mtnk904x.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 07 Oct 2021 20:10:22 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Simen Heggestøyl <simenheg@runbox.com> writes:
>
>>> Are there any plans to fix or at least revert this behaviour?
>>
>> This bug has been biting me too since switching to the emacs-28 branch.
>>
>> I agree with Manuel that it should be reverted until a fix is ready.
>
> Yup. There's been several patches here, though, so I'm not quite sure
> what to revert. Can you propose a patch that fixes this?
Peter's suggestion to remove the StartupWMClass line from
emacsclient.desktop fixes the "Emacs" launcher:
> I’m not sure what else to suggest. We can revert the fix to 49259
> (or, more sensibly, remove StartupWMClass from emacsclient.desktop
> entirely), but that doesn’t really help, since it’d cause the opposite
> problem that people who favourite “Emacs (Client)” would end up with a
> duplicate “Emacs” icon.
But as he says, it flips the bug around to hit users of the new "Emacs
(Client)" launcher instead...
Deleting emacsclient.desktop would bring back the behavior of Emacs 27 I
suppose, but I don't know whether having a slightly buggy "Emacs
(Client)" launcher is better than having no "Emacs (Client)" launcher at
all.
next prev parent reply other threads:[~2021-10-08 13:02 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
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 [this message]
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=87r1cvwtyb.fsf@runbox.com \
--to=simenheg@runbox.com \
--cc=49505@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).