From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [DISCUSSION] Possible inclusion of org-capture.el into Emacs core
Date: Sat, 13 Jul 2024 22:37:03 +0700 [thread overview]
Message-ID: <v6u6v0$m1h$1@ciao.gmane.io> (raw)
In-Reply-To: <87bka7c2e0.fsf@localhost>
I have dropped emacs-devel from Cc.
On 30/12/2023 19:15, Ihor Radchenko wrote:
> With org-protocol, one can also make Emacs receive data from browser and
> perform any action defined by custom handler function - all fully
> configurable and not necessarily related to Org mode.
and
Ihor Radchenko [SUMMARY] #8 [[bbb:OrgMeetup]] on Wed, June 12, 19:00
UTC+3. Sat, 22 Jun 2024 08:32:40 +0000.
<https://list.orgmode.org/87h6dlidhz.fsf@localhost>
> - Splitting Org into multiple small libraries is also a step forward
> toward more modular Org and to converting some Org-specific
> libraries to proper Emacs libraries, as requested by RMS:
> https://list.orgmode.org/E1kIkxv-0007iy-Av@fencepost.gnu.org/
[...]
> - org-protocol :: Processing external input into Emacs (from
> command line, from clicked Urls as url handler). Unlike
> running commands directly (which is unsafe), =org-protocol= can
> be used for safe interaction with external processes
I have nothing against adding org-capture to Emacs core, but I think
org-protocol should be just obsoleted. Since `server-eval-args-left' has
been added to emacs-30, hacks from org-protocol have a little value. The
new feature allows to implement handlers of URL schemes in a safe way
and to avoid backslash hell similar to emacsclient-mail.desktop.
A tiny package may be created for convenience to have single .desktop
file for all URI protocols (mailto:, org-protocol:). Leaving aside
tricks with --display, handler should be like
emacsclient --eval "(handle-url)" %u
or %U for multiple URLs. Packages just register supported protocols in
e.g. an alist and the dispatcher calls a function for matched scheme
with an argument from `server-eval-args-left'.
next prev parent reply other threads:[~2024-07-13 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875y0i7e43.fsf@hoowl.se>
[not found] ` <E1rJPu5-0006ML-UM@fencepost.gnu.org>
2023-12-30 12:15 ` [DISCUSSION] Possible inclusion of org-capture.el into Emacs core (was: [ELPA] New package: jami-bot and org-jami-bot) Ihor Radchenko
2023-12-30 17:43 ` Stefan Kangas
2024-01-01 3:34 ` Richard Stallman
2024-01-01 3:59 ` Richard Stallman
2024-01-01 14:05 ` Ihor Radchenko
2024-07-13 15:37 ` Max Nikulin [this message]
2023-12-30 12:43 ` [DISCUSSION] org-capture.el vs remember.el " Ihor Radchenko
2023-12-30 17:20 ` Stefan Kangas
2023-12-30 19:16 ` João Távora
2023-12-30 19:19 ` João Távora
2023-12-31 18:05 ` Adam Porter
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='v6u6v0$m1h$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@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/org-mode.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).