unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robin Tarsiger <rtt@dasyatidae.com>
To: emacs-devel@gnu.org
Subject: Re: GUI X-FreeDesktop integration
Date: Sun, 16 May 2021 05:46:27 -0500	[thread overview]
Message-ID: <c47f707d-e428-01db-ae5a-a1898b19580b@dasyatidae.com> (raw)
In-Reply-To: <20210516043619.5n6abchkqcpojzlc@E15-2016.optimum.net>

Boruch Baum wrote:
> My suggestion would be: Connect to an Emacs server.
> 
> But, I'd prefer that the emacsclient developers decide.

I would like to advance "Open a window in an existing Emacs
editor session" or something along those lines as closer to
the high-level user intent involved, with "and the Emacs
server must be running for this to work" as just a background
precondition. "connect to a server" is easy to interpret as
accessing a third-party network resource, on the surface,
and desktop entry descriptions may be displayed well out
of context as part of lists of other applications. (That
is also why I suggest "window" instead of "frame" above;
the description is desktop-environment-facing, so I would
use that terminology preferentially to Emacs-native terms.)

There's a separate question of whether autolaunch (-a "")
should be enabled. Boruch's initial suggestion included it,
but the current Git version doesn't. On balance, I'd tend
to think of it as less surprising from a desktop perspective
for it to be enabled. 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... that would mirror the
behavior of e.g. LibreOffice, Firefox, and many other popular
applications. In that case, you just have something like
"Edit text using Emacs". Or perhaps something longer with
a bit more sparkle to it: imagine a user seeing this entry
and asking "why would I want to edit text using Emacs rather
than something else?"---if there's short-enough phrasing that
can hint at an answer...

-RTT



  reply	other threads:[~2021-05-16 10:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14  3:18 GUI X-FreeDesktop integration 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 [this message]
2021-05-16 20:07           ` Matthias Meulien
  -- strict thread matches above, loose matches on Subject: below --
2021-05-25 21:34 Peter Oliver
2021-05-26  8:49 ` Robert Pluim
2021-05-26 12:14 ` Peter Oliver
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
2021-08-12 12:42 Manuel Uberti
2021-08-12 12:51 ` Eli Zaretskii
2021-08-12 12:58   ` 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=c47f707d-e428-01db-ae5a-a1898b19580b@dasyatidae.com \
    --to=rtt@dasyatidae.com \
    --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).