From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: bjorn.bidar@thaodan.de, stefankangas@gmail.com, 65469@debbugs.gnu.org
Subject: bug#65469: [PATCH] * etc/emacsclient.desktop: Make Emacs default application for org-protocol
Date: Tue, 19 Sep 2023 17:40:17 +0300 [thread overview]
Message-ID: <83a5ticjla.fsf@gnu.org> (raw)
In-Reply-To: <871qeunu1u.fsf@localhost> (message from Ihor Radchenko on Tue, 19 Sep 2023 13:58:53 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: bjorn.bidar@thaodan.de, 65469@debbugs.gnu.org, stefankangas@gmail.com
> Date: Tue, 19 Sep 2023 13:58:53 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> > Is this related to the issue with org-protocol?
> >>
> >> ...
> >> With the discussed patch, e.g. Firefox will automatically use Emacs when
> >> clicking on the above bookmarklet. Then, strictly speaking, it is not
> >> necessary for the GNU/Linux system to be fully XDG-compiant. It will be
> >> enough that (1) Emacs provides .desktop file; (2) Linux has xdg-open and
> >> its dependencies installed; (3) Firefox makes use of xdg-open.
> >
> > I don't understand what should the NEWS entry about org-protocol
> > support say, in addition to what it already says, to cover these
> > factoids. The NEWS entry is about the emacsclient.desktop file and
> > its contribution to automatic support of org-protocol; isn't what you
> > say above part of that automatic support?
>
> I guess it depends on the level of precision you want to have in the
> NEWS entry. For me, the NEWS entry sounds good enough, but I wanted to
> make things more clear after Björn's comment.
So what is imprecise in the wording I suggested a couple of messages
ago?
next prev parent reply other threads:[~2023-09-19 14:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 9:30 bug#65469: [PATCH] * etc/emacsclient.desktop: Make Emacs default application for org-protocol Ihor Radchenko
2023-08-23 22:39 ` Stefan Kangas
2023-09-01 18:50 ` Stefan Kangas
2023-09-17 13:09 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-17 13:16 ` Stefan Kangas
2023-09-17 14:18 ` Eli Zaretskii
2023-09-17 14:31 ` Stefan Kangas
2023-09-18 8:30 ` Ihor Radchenko
2023-09-18 11:02 ` Stefan Kangas
2023-09-18 11:15 ` Eli Zaretskii
2023-09-18 11:18 ` Stefan Kangas
2023-09-18 13:00 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 13:20 ` Ihor Radchenko
2023-09-18 13:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 14:33 ` Eli Zaretskii
2023-09-18 23:04 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-19 2:31 ` Eli Zaretskii
2023-09-19 7:59 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-19 11:06 ` Eli Zaretskii
2023-09-19 11:21 ` Ihor Radchenko
2023-09-19 12:24 ` Eli Zaretskii
2023-09-19 13:16 ` Ihor Radchenko
2023-09-19 13:50 ` Eli Zaretskii
2023-09-19 13:58 ` Ihor Radchenko
2023-09-19 14:40 ` Eli Zaretskii [this message]
2023-09-19 21:26 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-20 9:32 ` Ihor Radchenko
2023-09-20 13:39 ` Eli Zaretskii
2023-09-20 14:01 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-20 15:01 ` Eli Zaretskii
2023-09-23 21:35 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-20 22:41 ` Stefan Kangas
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=83a5ticjla.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65469@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=stefankangas@gmail.com \
--cc=yantar92@posteo.net \
/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).