From: chris <email@example.com>
Subject: Re: looking for examples of `org-capture-templates` working with `org-protocol://capture`
Date: Mon, 31 Jan 2022 04:07:01 +0100 [thread overview]
Message-ID: <4933995.AmxDJHG10n@pluto> (raw)
[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]
On Monday, 31 January 2022 03:30:41 CET chris wrote:
> When you do
> `emacsclient "org-protocol://capture?
> I don't understand at all how you make use of `url` `title` and `body` in
> `org- capture-template`.
> I understand there is some sort of "encoding" that doesn't make use of the
> keywords `url` `title` or `body`, but it's dense.
> There are no indications of how to do that here:
> I haven't found any example that I've been able to reproduce in the whole
> web. I've spent hours on the documentation and the source code of
> ] And I have absolutely no idea of how to use `url` `title` and `body` in
> `org-capture- template`.
The last example in https://blog.jethro.dev/posts/capturing_inbox/, namely:
`(("l" "org-protocol-capture" entry
"* TODO [[%:link][%:description]]\n\n %i"
Seems to work consistently with:
`xdg-open "org-protocol://capture?template=l&url=URL$(date --iso-8601=s)&title=TITLE$
Provided I have opened at least one org buffer before hand, otherwise it opens a buffer
` at what point it can get messy. Probably I have to "start" somehow "org-mode" first, and
it doesn't get enough started from my `init.el`.
Goal is to have the capturing work in the background, with emacs started as a daemon,
but with no opened emacsclient frame:
capture, simply, silently, unobtrusively.
>  https://orgmode.org/manual/The-capture-protocol.html
[-- Attachment #2: Type: text/html, Size: 5400 bytes --]
next prev parent reply other threads:[~2022-01-31 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 2:30 chris
2022-01-31 3:07 ` chris [this message]
2022-01-31 4:23 ` chris
2022-02-03 12:57 ` Max Nikulin
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).