From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65469@debbugs.gnu.org, yantar92@posteo.net, stefankangas@gmail.com
Subject: bug#65469: [PATCH] * etc/emacsclient.desktop: Make Emacs default application for org-protocol
Date: Tue, 19 Sep 2023 10:59:41 +0300 [thread overview]
Message-ID: <877comr3te.fsf@thaodan.de> (raw)
In-Reply-To: <837comevw5.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 19 Sep 2023 05:31:38 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Björn Bidar <bjorn.bidar@thaodan.de>
>> Cc: yantar92@posteo.net, 65469@debbugs.gnu.org,
>> stefankangas@gmail.com
>> Date: Tue, 19 Sep 2023 02:04:52 +0300
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> It applies to all operating system that use desktop environments
>> >> that comply with XDG so for example also BSD.
>> >
>> > Only XDG-compliant desktops? nothing else?
>>
>> Well only those that handle xdg desktop files specific uri type
>> handlers e.g. Gnome, KDE, Xfce etc.
>>
>> Not sure if there's something such as "fully XDG-compliant".
>>
>> My phrasing only intended to explain that in theory any operating
>> system
>> that uses xdg compliant desktop environments works with the change,
>> not
>> just GNU/QT/GTK/KDE/GNOME Linux.
>
> Thanks, but I'm looking for wording that we should put in NEWS. How
> would you categorize the systems which can support these desktop files
> in words that will be understood by readers of NEWS?
What about Unix and Unix-like systems excluding macOS?
next prev parent reply other threads:[~2023-09-19 7:59 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 [this message]
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
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=877comr3te.fsf@thaodan.de \
--to=bug-gnu-emacs@gnu.org \
--cc=65469@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--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).