emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Allen Li <vianchielfaura@gmail.com>
Cc: emacs-orgmode@gnu.org, Carl Bolduc <cbol@me.com>,
	Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: [PATCH] Update documentation on org-protocol template placeholders
Date: Tue, 17 Oct 2017 10:01:26 +0200	[thread overview]
Message-ID: <87376iyzhl.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJr1M6ePD5ZMxy4ADd34gg64fiX7=Wsgq=4i+6kRWtmyVEPrsw@mail.gmail.com> (Allen Li's message of "Sun, 15 Oct 2017 15:55:37 -0700")

Hello,

Allen Li <vianchielfaura@gmail.com> writes:

> * doc/org.texi (@code{capture} protocol): Fix placeholder names
> (Template expansion): Add org-protocol placeholders
>
> * lisp/org.el (org-store-link-plist): Fix docstring grammar
> (org-store-link-props): Fix docstring grammar

Thank you.

> +The following template placeholders are available:
> +
> +@example
> +%:link          The URL
> +%:description   The webpage title
> +%:annotation    Equivalent to [[%:link][%:description]]
> +%i              The selected text
> +@end example

This is not directly related to your patch, but isn't something wrong
here? 

I.e., shouldn't Org Protocol be able to capture arbitrary keywords
according to the attributes of the "org-protocol" link? What is the
point of using

  ?url=...&title=...&body=...

if you cannot access directly to :url, :title and :body from the capture
template thereafter?

Disclaimer: I'm not using Org Protocol at all so I may be missing
something.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2017-10-17  8:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-15 22:55 [PATCH] Update documentation on org-protocol template placeholders Allen Li
2017-10-17  8:01 ` Nicolas Goaziou [this message]
2017-10-17 18:33   ` Allen Li
2017-10-17 21:32     ` Nicolas Goaziou

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=87376iyzhl.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=cbol@me.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=vianchielfaura@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 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).