From: Konstantin Kliakhandler <kosta@slumpy.org>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: New Chrome Extension
Date: Tue, 7 Jul 2015 20:31:58 +0300 [thread overview]
Message-ID: <CAH+LVpkxFW8tBR5PHC-hSz-Cdzrwbikye67-TwxPpfLV__3irg@mail.gmail.com> (raw)
In-Reply-To: <m27fqbopqi.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]
Great - the %i is what gets interpolated into the pasted text.
If you don't specify a template letter, as in the setup pages, then the
link is sent to the same place as it would by org-store-link ("C-c l" if
you use the suggested bindings). Personally, I find it less useful in my
workflow, as I would then need to start a new capture and insert the link.
I can understand however why someone else would find that useful. When I
(or someone else) add a configuration page, this should be easy to change.
Cheers,
Kosta
On Jul 7, 2015 8:13 PM, "Ken Mankoff" <mankoff@gmail.com> wrote:
>
> Selected text works with your capture templates. Thanks for sending them.
>
> FYI I notice the "test" on the org-protocol.el setup pages uses this:
>
> document.location.href='org-protocol://capture://'+makeUrl();
>
> While yours uses:
>
> capture:/L/...
>
> If you don't specify "L" or "c" then would it let me choose which template
> the capture gets sent to? Seems like it might be an extra keystroke to then
> choose the template, but also more powerful...
>
> -k.
>
>
> On 2015-07-07 at 12:57, Konstantin Kliakhandler <kosta@slumpy.org> wrote:
> > Hello Ken,
> >
> > The first user, hurrah!
> >
> > You were right to add the capture templates - I will update the docs to
> be
> > more clear about that. I think the first thing to add to the extension
> now
> > that it is in the open is to add configuration for the targets...
> >
> > Here are the templates that I use (I need to replace the captured on:
> with
> > a property at some point, but this is beside the point):
> >
> > ("L" "Protocol Link" entry (file+headline ,(concat org-directory "
> notes.org")
> > "Inbox") "* %? [[%:link][%:description]] \nCaptured On: %U")
> >
> > ("p" "Protocol" entry (file+headline ,(concat org-directory "notes.org")
> > "Inbox")
> > "* %^{Title}\nSource: %u, %c\n
> > #+BEGIN_QUOTE\n%i\n#+END_QUOTE\n\n\n%?")
> >
> > I can't recall at the moment why I use the nicer format replacements for
> > the link and the shorter for the full quote, and it might not matter.
> Could
> > you try to make your "p" template similar to mine and see if it works?
> > Alternatively, can you paste the templates you used?
> >
> > Cheers,
> > Kosta
>
>
[-- Attachment #2: Type: text/html, Size: 3131 bytes --]
prev parent reply other threads:[~2015-07-07 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 15:44 New Chrome Extension Konstantin Kliakhandler
2015-07-07 16:16 ` Ken Mankoff
2015-07-07 16:24 ` Ken Mankoff
2015-07-07 16:57 ` Konstantin Kliakhandler
2015-07-07 17:13 ` Ken Mankoff
2015-07-07 17:31 ` Konstantin Kliakhandler [this message]
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=CAH+LVpkxFW8tBR5PHC-hSz-Cdzrwbikye67-TwxPpfLV__3irg@mail.gmail.com \
--to=kosta@slumpy.org \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@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).