From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tim Ruffing <public@timruffing.de>
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: Wed, 25 May 2022 02:16:55 +0200 [thread overview]
Message-ID: <87k0aafoug.fsf@gnus.org> (raw)
In-Reply-To: <8e5d9ea72584f981124ade5c69ec7162751723fe.camel@timruffing.de> (Tim Ruffing's message of "Tue, 24 May 2022 14:33:17 +0200")
Tim Ruffing <public@timruffing.de> writes:
> 1. Unify the .desktop files
>
> I know this has been tried already and was reverted because that
> particular approach has forced users into using the daemon, which I
> fully agree was not a good idea. What we could do instead is to have
> have a single emacs.desktop that simply does the following:
>
> Try to connect to daemon and create a new frame, if there's no daemon,
> just launch a new instance (e.g., using emacsclient -a emacs).
[...]
> The only drawback of this approach is that ideally "New Window" would
> bring up a just a new frame but this will work only in daemon mode. In
> non-daemon mode, you'll get a new instance.
I think this sounds like a sound approach. Can you prepare a patch for
this so we can try it out?
> But I'm not sure if this could be solved quickly because I'm not sure
> if there's a way to ask a non-daemon emacs to create a new frame. I
> think in the long-term we could for example use D-Bus activation [1]
> and make non-daemon emacs expose a dbus service that can create frames.
> But that's a larger project. Ideally there would be a "semi-daemon"
> mode, which is in between the daemon mode and the normal mode: The
> first invocation launches a daemon, further invocations (e.g., using
> emacsclient, or dbus) would just create new frames BUT if you close the
> last frame, no daemon will stay around. This would exactly match the
> behavior of other desktop applications.
Yes, that'd be nice. Using dbus for this (perhaps via emacsclient?)
might be the right approach here.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-25 0:16 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 [this message]
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=87k0aafoug.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=49505@debbugs.gnu.org \
--cc=manuel.uberti@inventati.org \
--cc=p.d.oliver@mavit.org.uk \
--cc=public@timruffing.de \
/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).