all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: GUI X-FreeDesktop integration
Date: Fri, 14 May 2021 18:29:34 +0700	[thread overview]
Message-ID: <CAP_d_8VYfeoCERxRx11CJecKB+H=vvemBBTG0Qzejvxp_mzTxA@mail.gmail.com> (raw)
In-Reply-To: <87bl9dwy0a.fsf@fastmail.fm>

On Fri, 14 May 2021 at 14:55, Joost Kremers <joostkremers@fastmail.fm> wrote:

> On Fri, May 14 2021, Eli Zaretskii wrote:
>
> > Does emacs.desktop work for emacsclient invocations as well?  If so,
> > why did we add emacsclient.desktop on master?  (I know nothing about
> > GNOME desktop and its use protocols.)
>
> I don't know, and I don't have a clue how to go about testing that. AFAIK a
> .desktop file allows you to put a launcher in the dock and in the Applications
> menu of your GUI and that's it.

No, that’s not (only) it. A .desktop file:

* Puts a launcher in the Applications menu so you can launch the application.
* Optionally, associates an application with a set of MIME types so
you can open documents with that application from your file manager,
mail client, and other applications.
* Optionally, associates an application with an URL scheme so you can
open URLs in that application.

A simple .desktop file only has a single command line defined. It is
also possible to define multiple actions with different command lines
and supporting launcher GUIs will expose those actions to the user,
but etc/emacs.desktop in current master does not use this capability.

https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.1.html



  reply	other threads:[~2021-05-14 11:29 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 [this message]
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
  -- 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP_d_8VYfeoCERxRx11CJecKB+H=vvemBBTG0Qzejvxp_mzTxA@mail.gmail.com' \
    --to=yuri.v.khan@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joostkremers@fastmail.fm \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.