From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, bjorn.bidar@thaodan.de,
stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: Generic Elisp mechanism to declare file/URI handlers for Emacs
Date: Tue, 19 Sep 2023 13:56:23 +0000 [thread overview]
Message-ID: <874jjqnu60.fsf@localhost> (raw)
In-Reply-To: <83o7hycm3p.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> ...
> So I don't see how we could offer something like that for Windows; we
> learned long ago that including scripts or programs that write into
> the Registry is a two-edged sword, so we refrain from doing that
> nowadays.
I see. Is it the same problem on MacOS?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-09-19 13:56 UTC|newest]
Thread overview: 45+ 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-19 11:14 ` Generic Elisp mechanism to declare file/URI handlers for Emacs (was: bug#65469: [PATCH] * etc/emacsclient.desktop: Make Emacs default application for org-protocol) Ihor Radchenko
2023-09-19 11:44 ` Generic Elisp mechanism to declare file/URI handlers for Emacs Po Lu
2023-09-19 13:06 ` Ihor Radchenko
2023-09-19 13:25 ` Po Lu
2023-09-20 9:26 ` Ihor Radchenko
2023-09-20 9:57 ` Po Lu
2023-09-20 11:17 ` Should Emacs declare itself as being able to open all the text/* mimetypes? (was: Generic Elisp mechanism to declare file/URI handlers for Emacs) Ihor Radchenko
2023-09-20 12:23 ` Should Emacs declare itself as being able to open all the text/* mimetypes? Po Lu
2023-09-20 12:38 ` Ihor Radchenko
2023-09-19 13:46 ` Generic Elisp mechanism to declare file/URI handlers for Emacs Eli Zaretskii
2023-09-19 13:56 ` Ihor Radchenko [this message]
2023-09-20 11:15 ` Eli Zaretskii
2023-09-19 16:28 ` Generic Elisp mechanism to declare file/URI handlers for Emacs (was: bug#65469: [PATCH] * etc/emacsclient.desktop: Make Emacs default application for org-protocol) Jim Porter
2023-09-18 14:33 ` bug#65469: [PATCH] * etc/emacsclient.desktop: Make Emacs default application for org-protocol 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jjqnu60.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.com \
/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.