From: Peter Oliver <p.d.oliver@mavit.org.uk>
To: emacs-devel@gnu.org
Subject: Re: GUI X-FreeDesktop integration
Date: Wed, 26 May 2021 13:14:23 +0100 (BST) [thread overview]
Message-ID: <573eb311-e0f6-2216-4298-458ae8ab827b@froglet.home.mavit.org.uk> (raw)
In-Reply-To: <7f52af92-4fb5-74b4-232a-eabfa315ac0@froglet.home.mavit.org.uk>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On Tue, 25 May 2021, Peter Oliver wrote:
> On Sunday 16th May, Robin Tarsiger wrote:
>
>> In fact, the _least_ surprising from
>> an XDG/FDO perspective would actually be to _only_ expose
>> a "client+autolaunch" desktop entry and just call that the
>> point of integration for Emacs.
>
> Agreed. Attached is a patch which achieves this.
After a bit more testing, I discovered a snag.
I believe that the default behaviour when opening a file from a desktop’s file manager should be to open it in an existing GUI frame if one exists, or a new GUI frame if one does not. Clicking Emacs in a desktop’s application launcher should open a new GUI frame.
The trouble is that, if Emacs is running as a daemon with no frames, `emacsclient /path/to/foo` will create a new TTY frame rather than a GUI frame. Should this behaviour be changed so that a GUI frame is preferred if $DISPLAY is set? While we’re here, should we report an error if there is no display and no TTY?
--
Peter Oliver
next prev parent reply other threads:[~2021-05-26 12:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 21:34 GUI X-FreeDesktop integration Peter Oliver
2021-05-26 8:49 ` Robert Pluim
2021-05-26 12:14 ` Peter Oliver [this message]
2021-05-26 12:19 ` Eli Zaretskii
2021-05-28 12:54 ` Peter Oliver
2021-05-28 13:03 ` Eli Zaretskii
2021-05-28 18:49 ` chad
2021-05-28 19:16 ` Eli Zaretskii
2021-05-28 20:05 ` chad
2021-05-29 6:01 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2021-08-12 12:42 Manuel Uberti
2021-08-12 12:51 ` Eli Zaretskii
2021-08-12 12:58 ` Lars Ingebrigtsen
2021-05-14 3:18 Boruch Baum
2021-05-14 3:46 ` Stefan Monnier
2021-05-16 3:26 ` Boruch Baum
2021-05-14 6:45 ` Eli Zaretskii
2021-05-14 7:20 ` Joost Kremers
2021-05-14 7:41 ` Eli Zaretskii
2021-05-14 7:53 ` Joost Kremers
2021-05-14 11:29 ` Yuri Khan
2021-05-14 13:51 ` Stefan Monnier
2021-05-16 3:33 ` Boruch Baum
2021-05-16 4:25 ` Eli Zaretskii
2021-05-16 4:36 ` Boruch Baum
2021-05-16 10:46 ` Robin Tarsiger
2021-05-16 20:07 ` Matthias Meulien
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=573eb311-e0f6-2216-4298-458ae8ab827b@froglet.home.mavit.org.uk \
--to=p.d.oliver@mavit.org.uk \
--cc=emacs-devel@gnu.org \
/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).